Re: authentication problems - Mailing list pgsql-admin

From Russ McBride
Subject Re: authentication problems
Date
Msg-id v04210103b7dc258398f3@[64.170.120.108]
Whole thread Raw
In response to Re: authentication problems  ("Nick Fankhauser" <nickf@ontko.com>)
Responses Re: authentication problems  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: authentication problems  ("Chad R. Larson" <chad@eldocomp.com>)
Re: authentication problems  ("Chad R. Larson" <chad@eldocomp.com>)
List pgsql-admin
Hi,

I'm going to restate the situation since there was some confusion,
judging from a couple of responses.

The goal-- The goal is to be able to connect to my database from the
very machine where the database sits, without worrying about what my
ip settings are (I switch them around a bunch for various reasons).

The normal solution-- set the following line in the pg_hba.conf file,
which should be there by default:
host       all       127.0.0.1      255.255.255.255         trust
This should allow the localhost to connect regardless of its ip
address setting.

The problem-- the above setting doesn't work as it should.  Even with
the above line I can only connect if I manually type in the exact ip
address of the machine (which is both the client machine and the
posgresql server).

Nick said:
>
>If you can't ping localhost, or it doesn't resolve to 127.0.0.1, then you
>know the problem is at the operating system/network level & postgres and
>JDBC are probably just fine.
>
>-Nick
>

Thanks for the troubleshooting idea Nick.  I can ping localhost which
does show up as 127.0.0.1.  The error message I get is:
No entry in pg_hba.conf_file for 169.245.10.10 [or whatever ip
address I happen to be using at the time] for user: postgres
database: testdb

I'm baffled.  Any remotely feasible other troubleshooting ideas are
appreciated.


Russ



pgsql-admin by date:

Previous
From: "Nick Fankhauser"
Date:
Subject: Re: authentication problems
Next
From: Tom Lane
Date:
Subject: Re: authentication problems